Skip to content

Support explicit JsType annotations field or class#102

Draft
rocketraman wants to merge 1 commit intovoize-gmbh:mainfrom
rocketraman:rg/explicit-js-type
Draft

Support explicit JsType annotations field or class#102
rocketraman wants to merge 1 commit intovoize-gmbh:mainfrom
rocketraman:rg/explicit-js-type

Conversation

@rocketraman
Copy link
Copy Markdown
Contributor

@rocketraman rocketraman commented Jun 26, 2025

Support @jstype annotations at field or class level which allow users to specify any type for that field or class. This is useful when a type is serialized in a non-standard way and the user wants to use a different TypeScript mapping than the one inferred by the class structure.

This PR is draft until approved in principal by @Legion2 or @erksch . Once approved, I will add the logic for the type generation and mapping functions, and add docs to the README and add tests.

Resolves #101

We now support @jstype annotations at field or class level which
allow users to specify any type for that field or class. This is useful
when a type is serialized in a non-standard way and the user wants
to use a different TypeScript mapping than the one inferred by the
class structure.
@Legion2
Copy link
Copy Markdown
Member

Legion2 commented Jun 28, 2025

Sounds good 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature] Customize Typescript mapping: expand usage of @JsType

2 participants